Log Categories

Studio and Runtime/Agile Desktop publish diagnostic messages based on the application diagnostics level you selected and application log categories. For more information, see Diagnostics Configuration. This topic describes the log settings and categories available for Studio and Runtime/Agile Desktop.

Log Settings

For each log category, you can specify the following levels. The default is Info.

Level	Type of tracked events
Critical (0)	This setting records negative events which indicate unexpected processing or an error. Only certain unhandled exceptions are reported.
Error (1)	This setting records error messages, indicating the application was not able to perform a task as expected. The application is, however, still running.
Warning (2)	This setting records both error and warning messages.
Info (3)	This setting records error, warning, and informational messages. It includes successful milestones of application execution, regardless of whether the application is working properly, and provides an overview of what happened.
Verbose (4)	This setting records error, warning, informational messages and verbose debugging output. Note: This option generates a large number of messages and is not recommended when used with multiple trace source selections.

Note: Each level includes messages captured by the previous level. For example, selecting Verbose includes Info, Warning, Error, and Critical messages. If you choose Critical, Error, or Warning, the logs will be blank under normal operating conditions.

The categories are pre-defined. The log category settings are stored in the StudioConfig.xml and RuntimeConfig.xml files. The log categories and levels are applied to messages output through OpenSpan diagnostics publishers.

Categories

Note: Studio adds categories as required during product updates. The following list may not include all of the categories available for your version of Studio and Runtime/Agile Desktop.

Category	Description
All Categories	All logged categories.
Default	Logs associated with any category not otherwise specified in this list.
Keys	Logging associated with the cloning of controls, which involves the generation of keys.
Matching	Logs regarding matching controls.
Adapters	Logs regarding general adapter information (for example when it starts or stops)
Java Adapter	Logs regarding the Java adapter.
Text Adapter	Logging associated with any text adapter.
Text Screens	Applies to a single log message which contains the contents of the previous and current screen.
Web Adapter	Logs associated with the web adapter.
Windows Adapter	Logs associated with the Windows adapter.
Windows Messages	Logs associated with the use Windows messages. These are invoked when Windows messages are used from one area to another.
Citrix Connector	Logs associated with the Citrix connector. Remote Proxy errors are messages generated when multiple contexts are used.
Remote Proxy	Logs used by the Remote Proxy function.
Automation	Logs associated with automations.
Serialization	Logs associated with the serialization of DesignComponents to and from XmlText.
Designer	Used when you need logging in classes that interact with the .NET designer stack.
Debugger	Logs associated with the debugged.
Deployment	Logs associated with deployment.
Office	Logs associated with Microsoft Office components.
Web Service	Logs used by the WebService component.
Service	Logs used by the ServiceClient component.
Studio	All of the categories below are for internal use by Studio development. Default Value Diagnostic Initialization Project Connectable Index Object Explorer Solution File Management Configuration User Data Transformer Attribute Provider Manifest Type Reference Configuration User Data Transformer Attribute Provider Manifest Type Reference Type Resolution Runtime Cloned Instance Broker Runtime Script Component Inspector Threading Security EventLog Licensing Virtual Broker